Skip to main content

Iframe How To's

How to's for the Iframe guide.

How to Use Iframe?

How to Use Iframe?

The following steps explain how to use the Iframe object on a form.

Add the Iframe Object to the Form

  1. Open the form design screen
  2. Go to the Toolbox panel
  3. Locate the Iframe object
  4. Add the object to the form using drag / drop

Define the Iframe URL

  1. Click the Iframe object added to the form
  2. The Property Viewer panel opens on the right
  3. Under the General tab:
    • Enter the URL address to be displayed
    • Example:
      https://www.example.com

Configure Size and Appearance

  • Height: The space the Iframe will occupy on the form
  • Width: Horizontal space usage
  • Scrolling behavior can be controlled via Scroll settings

These settings help the iframe content fit the form design.

Run the Form

  1. Build and Publish the project
  2. Open the form in the web interface
  3. Observe that the specified web page is loaded inside the iframe

Tips

  • For responsive designs, it can be used together with Auto Height / ScrollView
  • URLs with security restrictions may not open inside an iframe
  • For performance, use heavy pages carefully

What Is Iframe?

What Is Iframe?

Iframe is a form object that allows an external web page, an application-external URL, or other web content to be embedded and displayed directly on a form.

With this object, users can view:

  • Another website
  • External reports
  • Maps, dashboards, documentation pages
  • Internal web applications

directly within the form, without leaving it.

Iframe isolates its content within its own boundaries and operates independently without affecting the main form structure.

What Is It Used For?

  • Embedding external web pages into a form
  • Displaying reports, dashboards, or monitoring screens
  • Integrating maps, documentation, or help pages
  • Providing quick access to microservices or other applications

Key Features

  • External URL support
  • Configurable height and width
  • Scroll support
  • Secure isolation (iframe sandbox logic)
  • Running content independently from the form

Notes

  • The page to be displayed must allow iframe usage
  • Some websites may not open inside an iframe due to security restrictions
  • HTTPS forms are recommended when displaying HTTPS content

How to Use Client Enabled?

What is Client Enabled?

Client Enabled is a property that defines whether a form control is active (enabled) on the client side when the form is first loaded.
If it is set to True, the control is immediately usable by the user.
If it is set to False, the control is disabled and cannot be interacted with until a specific condition or rule activates it.

This property is especially useful for controlling the user’s interaction flow and applying dynamic behaviors using the Rule Manager.

What Does It Do?

The property allows developers to:

  • Control when a form control becomes interactive.
  • Prevent users from entering or changing data until prerequisites are met.
  • Dynamically enable or disable controls based on user input or logic.

Example Scenario — Conditional Activation

Scenario:
A form contains a checkbox called “I Accept Terms” and a text field called “Signature.”
The goal is to make the “Signature” field inactive until the user checks “I Accept Terms.”

Steps to Implement:

  1. Select the “Signature” field in the form editor.

  2. In the Properties panel, find the Client Enabled field.

  3. Set the value to False — the field will now be disabled by default when the form loads.

  4. Open the Rule Manager.

  5. Add a new rule:

    Condition:

Action:

  1. Save and publish the form.

Result:

  • When the form loads, the “Signature” field is disabled.
  • Once the user checks “I Accept Terms,” the field automatically becomes active and editable.

Behavior Summary

Property StateDescription
TrueThe control is active and ready for user interaction when the form loads.
FalseThe control is disabled at load time and can be enabled dynamically via rules or code.

Notes & Best Practices

  • Use the Client Enabled property to manage client-side interactivity without requiring server actions.
  • Combine it with Rule Manager to define when and how controls become active.
  • Remember: if server enablement is disabled, the client cannot enable the control even if Client Enabled is set to True.
  • By default, this property is set to True (active).

Summary

Client Enabled improves form usability by letting developers control when and how users interact with form controls.
It is essential for creating responsive, condition-based form experiences where user actions dynamically change the form’s state.